Efficiently handling tasks would implement a fast fucking application.
/shokai/tasks/efficiently-processing-tasks-is-fast-fucking-application-implementation.
The concept of efficient is often assumed to be "good" at first glance
However, there are disadvantages, the story goes.
If "user requests" are implemented before they are connected to other things, you end up with a pile of "features" that are not very consistent with each other.
This is hard to use.
Because acquisition cost is high for the user?
relevance
Ideas inspired by a single stimulus, but rather many connected things are important.
---
This page is auto-translated from /nishio/タスクを効率的に処理していくと高速にクソアプリを実装してしまう using DeepL. If you looks something interesting but the auto-translated English is not good enough to understand it, feel free to let me know at @nishio_en. I'm very happy to spread my thought to non-Japanese readers.